DOCUMENT:Q102603  04-NOV-1993  [W_NT]
TITLE   :Windows NT Doesn't Recognize Second Processor After Upgrading
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:

----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1
 - Microsoft Windows NT Advanced Server, version 3.1
----------------------------------------------------------------------

SYMPTOMS
========

After you upgrade COMPAQ SYSTEMPRO from a single processor to a dual
processor, Windows NT doesn't recognize the second processor.

CAUSE
=====

If you install Windows NT on a single-processor SYSTEMPRO, Setup
installs HAL.DLL and NTOSKRNL.EXE for a single-processor system. If
you then add a second processor, it is not recognized when you reboot.
On most other multi-processor systems that originally had a single
processor when Windows NT was installed, the multi-processor HAL and
kernel are installed. As a result, the second processor is recognized
automatically.

RESOLUTION
==========

To work around this problem, boot your computer from an MS-DOS command
prompt and copy HALSP.DLL from the original Windows NT disk(s) to the
%SystemRoot%\SYSTEM32 directory as HAL.DLL. Then, copy NTKRNLMP.EXE to
%SystemRoot%\SYSTEM32 directory as NTOSKRNL.EXE. If a kernel debugger
is connected, update the symbols on it.

Additional reference words: 3.10
KBCategory:
KBSubCategory: hrdwr

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1993.